Hosted email to Physical Exchange 2010 server?
I have a client that has hosted email and wants to get away from this and got to a physical exchange 2010 email server for there 35 users on site. How do i do this? how hard is it? Any and all instructions are welcomed
thanks in advance
Ehunt
November 24th, 2011 7:43pm
Hi Ehunt,
Migrating from a hosted email system to on-premises Exchange 2010 server I would approach that this way at high level:
1. Investigate if your client's network supports setting up an on-premises Exchange deployment, understand all the prerequisites (such as AD, Internet connection, firewall etc.).
Exchange Pre-Deployment Analyzer is your friend here: http://www.microsoft.com/download/en/details.aspx?id=11636
2. Be clear about the dependencies of placing a new Exchange server to the network, that includes things that Exchange dependent on (majority should be taken care by step 1) and things that will be dependent on the Exchange server. List them
all out and ensure you have a plan to make them all work after setting up the Exchange server.
3. Understand how you can extract the email data from the hosted email system and import the data to Exchange server. If client are using Outlook probably it would be as simple as exporting data to PST files. Exchange 2010 supports importing
PST files to users' mailboxes.
4. Understand the licensing implication, as your client will be paying for Exchange server licenses and CALs, and perhaps Outlook licenses if client haven't got Outlook software already. Exchange 2010 comes with standard and enterprise licenses, they
provide different feature sets, ensure you client are clear what they will get from different type of licenses.
5. Plan and deploy the Exchange Server 2010 to client's network. You can use Exchange Server Deployment Assistant (http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#Index)
for that, a very good tool.
6. Migrate the email data to Exchange server and migrate clients to Exchange server. With 35 users, you probably can do it all at a time. Or if you want more control and minimise the disruption, do it at batches.
7. Test and user support with possibly decommission of any client-side app for hosted email system
Microsoft TechNet library has hug amount of Exchange Server 2010 information that you can use, and don't forgot the Microsoft Exchange Team Blog at http://blogs.technet.com/b/exchange/.
Last you probably want to run a proof of concept exercise if you are not confident everything will work out correctly.
Regards.
Johnmen
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2011 10:11pm
Hi Ehunt,
Migrating from a hosted email system to on-premises Exchange 2010 server I would approach that this way at high level:
1. Investigate if your client's network supports setting up an on-premises Exchange deployment, understand all the prerequisites (such as AD, Internet connection, firewall etc.).
Exchange Pre-Deployment Analyzer is your friend here: http://www.microsoft.com/download/en/details.aspx?id=11636
2. Be clear about the dependencies of placing a new Exchange server to the network, that includes things that Exchange dependent on (majority should be taken care by step 1) and things that will be dependent on the Exchange server. List them
all out and ensure you have a plan to make them all work after setting up the Exchange server.
3. Understand how you can extract the email data from the hosted email system and import the data to Exchange server. If client are using Outlook probably it would be as simple as exporting data to PST files. Exchange 2010 supports importing
PST files to users' mailboxes.
4. Understand the licensing implication, as your client will be paying for Exchange server licenses and CALs, and perhaps Outlook licenses if client haven't got Outlook software already. Exchange 2010 comes with standard and enterprise licenses, they
provide different feature sets, ensure you client are clear what they will get from different type of licenses.
5. Plan and deploy the Exchange Server 2010 to client's network. You can use Exchange Server Deployment Assistant (http://technet.microsoft.com/en-us/exdeploy2010/default.aspx#Index)
for that, a very good tool.
6. Migrate the email data to Exchange server and migrate clients to Exchange server. With 35 users, you probably can do it all at a time. Or if you want more control and minimise the disruption, do it at batches.
7. Test and user support with possibly decommission of any client-side app for hosted email system
Microsoft TechNet library has hug amount of Exchange Server 2010 information that you can use, and don't forgot the Microsoft Exchange Team Blog at http://blogs.technet.com/b/exchange/.
Last you probably want to run a proof of concept exercise if you are not confident everything will work out correctly.
Regards.
Johnmen
November 25th, 2011 5:47am
Just additional information to Johnmen:
You might neec to contact your hosted environment support service for exporting the mailbox; or you can pose a question in
http://social.technet.microsoft.com/Forums/en-US/exchange2010hosters/threads
for licenses related affires, see
http://www.microsoft.com/licensing/contact-us.aspx.
Hope it is helpful.
Best Regards Fiona Liao E: v-fiolia@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2011 4:31am